Amazon Elastic Block Store (EBS)

Suitable when

When you need the flexibility to scale block storage quickly and easily.
When you need a secure, reliable and scalable storage for your applications

Unsuitable when
The data is needed to be accessed from multiple regions
When the application requires high throughput, low latency or frequent data access.

If you need to run ultimate, high scale application for frequently updated data with permanent recovery point update - use block storage especially if you are core Java, MSFT Net developer. It has faster input/output capabilities and rapid access, but limited only for current instance nor any external server call. It will not fit your demand for building in depth analytical system, cause missing build in data schema, and using separate data base for mapping metadata could slow and limit access. Since of 2000-th Elastic is more then classics, so is a choise of your architectore if it suit your business objective. There is no field for failure, so choose type block or object before you have started implementation. Works good for data warehousing of missiong critical parts of ERP and decision making apps.

It is well-suited for below uses:
1. Data Persistence
2. Backup and restore
3. DR testing
4. Disaster Recovery

It is less appropriate for below:
1. Multiple region or AZ developments
2. Big data
3. Data archiving

EBS has the ability to make data is efficiently saved, and it is treated with care. Zone availability is one of the most intriguing characteristics. When an instance is terminated, no data is lost. The starting time has been reduced. You can pause and resume the instance at any time. It is possible that utilizing an EBS AMI is more expensive than using a non-EBS AMI.

Data is handled with caution, and information is managed effectively. One of the most exciting aspects is the availability of zones. If the instance is terminated, your data will not be lost. It's simple to add more storage, remove storage, or switch between storage speeds.

Data is treated with care and information is kept efficiently. Adding extra storage, removing storage, or moving between storage speeds is easy. The availability of zones is one of the most intriguing elements. Your data will not be lost if the instance is terminated. Stopping and starting instances is possible. It has excellent uptime.

Data is stored efficiently and data is processed with caution. One of the most interesting features is zone availability. No data is lost when the instance is terminated. The startup time is shortened. You can stop and start the instance. Using an EBS AMI can be more costly than using a non-EBS AMI.

Information is stored efficiently and data is handled with care. One of the most interesting features is the availability of zones. If the instance is terminated, your data will not be lost. Boot time is reduced. Instances can be stopped and started. It may be more expensive to use an EBS AMI than to use a non-EBS AMI.

Information is efficiently stored, and data is carefully handled. Zone availability is one of the nicest features. If the instance is terminated, your data is not lost. Bootup time is reduced. Instances can be stopped and started. It is possible that utilizing EBS AMIs is more expensive than using non-EBS AMIs.

EBS proved quite beneficial in terms of keeping the data persistent especially in cases where you have capping in terms of storage on EC2 instance, one EBS can be connected to multiple EC2 instances which can act as an external hard drive important data can be pushed into it. These EBS blocks can be deployed into different availability zone so that in case one of the availability zones goes down others will be available to cater to the request.

Amazon Elastic Block storage is a great tool to augment your existing Amazon Elastic Compute Cloud and allows you a good way to add, move and adjust storage. It is great also for a back up solution for your virtual resources that are in the cloud to be used in cases of disaster recovery.